GCP Health
Google Cloud's healthcare offering centres on the Cloud Healthcare API, a managed service for storing and exchanging clinical data in standard formats, with the rest of the platform available for analytics on top.
Cloud Healthcare API
Data lives in datasets, which contain stores of three kinds:
FHIR stores
Managed FHIR servers supporting recent releases, with the standard REST API, search, profile validation, and streaming export to BigQuery.
HL7 v2 stores
Ingest and store HL7 v2 messages, with parsing into structured form and configurable schemas for message types.
DICOM stores
Medical imaging via DICOMweb — see imaging AI.
Around these: de-identification operations for FHIR and DICOM, Cloud IAM for access control, audit logging, and Pub/Sub notifications on data change (useful for building event-driven pipelines without polling).
Analytics path
The pattern most teams end up with:
FHIR store → streaming export → BigQuery → dbt / SQL → Looker Studio
BigQuery flattens FHIR resources into analysable tables. From there, Vertex AI covers model development if you are doing machine learning on the data — with the caveats in clinical AI and AI ethics applying in full.
Choosing a managed FHIR service
Advantages:
- No server operations, patching or capacity planning
- Managed scaling and backups
- Built-in de-identification and audit logging
- Direct analytics integration
Trade-offs to weigh honestly:
- Data residency. Regions are fixed; many countries require health data to remain onshore, which can rule the service out entirely.
- Cost model. Per-request and per-GB pricing behaves very differently from a fixed server; model it against your real query patterns.
- Version timing. You upgrade when the provider does. If you need two FHIR releases running in parallel during a migration, check that the service supports it.
- Portability. The FHIR API is standard, so resources move; IAM policy, de-identification configuration and pipelines do not.
Related
- AWS health and Azure health — the comparable services
- FHIR servers — self-hosted alternatives
- ISO 27799, GDPR — obligations that follow the data into the cloud
References
- Cloud Healthcare API — https://cloud.google.com/healthcare-api